services/control/server.js:257

• reconcileAutostart() ignores the Docker API status code for the stop request. If Docker returns a non-204/304 status, it will be treated as success and autostart intent may not actually be enforced.

        await dockerRequest('POST', `/containers/${container.Id}/stop`);

services/frontend/src/App.svelte:493

• Same simBusy race applies to stopSim: overlapping async actions can cause simBusy to be cleared by an earlier call while a later call is still pending. Guard against concurrent actions (or track busy per simulator).

  async function stopSim(id) {
    simBusy = id;

services/frontend/src/App.svelte:844

• While an action is in flight, other simulator buttons remain enabled (because disabled only matches the busy id). Combined with the simBusy race, this makes it easy to trigger overlapping actions that the UI state can't represent. Disabling all simulator actions while simBusy is non-null avoids this class of issues.

                  <button class="svc-reset" disabled={simBusy === sim.id} on:click={() => stopSim(sim.id)}>

services/frontend/src/App.svelte:848

• Same as above for the Launch button: leaving other rows enabled while one request is pending allows overlapping actions even though state is tracked with a single simBusy value.

                  <button class="svc-reset" disabled={simBusy === sim.id} on:click={() => launchSim(sim.id)}>

services/control/server.js:248

• shouldRunAutostartReconcile() writes the autostart stamp file before reconciliation has actually succeeded. If Docker is unreachable or simulator containers aren’t created yet, reconcileAutostart() returns false but the stamp has already been written, so subsequent retry attempts will be skipped and autostart intent may never be enforced for this stack instance.

async function shouldRunAutostartReconcile() {
  const stamp = STACK_INSTANCE || PROJECT;
  try {
    const prior = (await readFile(AUTOSTART_STAMP_FILE, 'utf8')).trim();
    if (prior === stamp) return false;

services/control/server.js:270

• reconcileAutostart() returns undefined when shouldRunAutostartReconcile() is false (already reconciled). scheduleAutostartReconcile() treats that as “not done” and will keep retrying pointlessly. Returning a boolean here avoids unnecessary retries and keeps the function’s return contract consistent.

async function reconcileAutostart() {
  if (!(await shouldRunAutostartReconcile())) return;
  let containers;

tests/acceptance/s13-theme-f-transport.spec.js:47

• The total timing assertion (elapsedMs < 30_000) can fail even when both individual waits succeed, because the test allows up to 30s for #stream-status and then up to another 30s for #state (sequential waits). If the DOM updates are staggered, elapsedMs can exceed 30s and make the test flaky.

    const started = Date.now();
    await page.goto('/gzweb/');
    await expect(page.locator('#stream-status')).toHaveText(/connected/i, { timeout: 30_000 });
    await expect(page.locator('#state')).toHaveText(/connected/i, { timeout: 30_000 });

    const elapsedMs = Date.now() - started;
    // Informative ceiling to keep deterministic CI signal while documenting
    // FR-F5 behavior in variable host environments.
    expect(elapsedMs).toBeLessThan(30_000);